Tree

There is a problem

1000 entries with tree-preservation-order field must match the reference field in the tree preservation order

1742

reference: 265-tree-1
name: 1742
tree-preservation-order: undefined
265-tpo-1
uprn
address-text
point: POINT (-0.940686 50.863404)
geometry: MULTIPOLYGON (((-0.940601 50.863395,-0.940605 50.863412,-0.940617 50.863427,-0.940635 50.863439,-0.940659 50.863447,-0.940685 50.863450,-0.940712 50.863447,-0.940736 50.863440,-0.940755 50.863428,-0.940767 50.863413,-0.940772 50.863396,-0.940768 50.863380,-0.940756 50.863365,-0.940738 50.863352,-0.940714 50.863345,-0.940688 50.863342,-0.940661 50.863344,-0.940637 50.863352,-0.940618 50.863363,-0.940606 50.863378,-0.940601 50.863395)))
notes
felled-date
entry-date: 2026-08-06
start-date
end-date

How to fix this issue

Your data is missing a tree-preservation-order.

The tree guidance explains how to fix the issue:

tree-preservation-order

The reference for the tree preservation order that affects this tree.

Example: TPO1

This diagram shows the relationship between the tree preservation order dataset and the tree dataset. The reference value from your tree preservation order dataset needs to match the tree-preservation-order value in your tree dataset.

How to improve East Hampshire District Council’s data

Fix the errors indicated
Use the check service to make sure the data meets the standard
Publish the updated data on the endpoint URL